GET Paginated GeoBlocking Rules For Project
Overview
The following table contains important information about the GET method in regards to receiving the paginated geoblocking rules For project.
| GET Paginated GeoBlocking Rules For Project | |
|---|---|
| Method | GET |
| URL or Endpoint | /api/projects/projectId/geo-blocking-rules |
| Headers | Authorization |
| Parameters | search, order, insertedDate, page, take, api-version, projectId |
| Body | Not Applicable |
The description of the URL parameters is as follows:
| URL Parameter Name | Mandatory | Type | Description |
|---|---|---|---|
| search | string | A word you want to filter. | |
| order | string | Indicates whether the content is ordered by ascending or descending. | |
| insertedDate | Date | Date when inserted. | |
| page | integer($int32) | Page where the method makes the request. | |
| take | integer($int32) | Number of geoblockings to take. | |
| api-version | No | string | Correct api-version. |
| projectId | Yes | string | Unique Id of the project. |
Request Body
The request does not contain a request body
Response
If the action is successful, the service sends back an HTTP 200 or 201 response.
Errors
For information about the errors that are common to all actions, see Common Errors:
HTTP Status Code 400: Bad Request
HTTP Status Code 401: Unauthorized
HTTP Status Code 403: Forbidden
HTTP Status Code 404: Result Not Found
HTTP Status Code 500: Internal Server Error
HTTP Status Code 503: Backend Fetch Failed